home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
os2
/
gigo0714.zip
/
REQFILES.FAQ
< prev
next >
Wrap
Text File
|
1994-08-29
|
2KB
|
42 lines
Q: What format are the FUNCTION.REQ and FUNCTION.REP files
Q: How do I use the USER ... FUNCTION ... commands?
When GIGO encounters email to a USER .. FUNCTION command,
it saves the incoming message, verbatim, as FUNCTION.REQ.
It then shells out, runs the specified command, and then
looks to see if FUNCTION.REP is present. If it is, it is
sent back to the person requesting the service.
It's all straight ascii, nothin' fancy at all.
Q: What is the structure of .REQ files for fileserv request?
A: The structure of the .REQ file is very similiar to a Binkley
flo file. The first line _must_ be the email address that the
resulting messages should be sent to. The remaining lines can
be comments that are sent to the user (lines starting with ; are
considered comments). Or, they may be file names to be sent.
If the path is not specified, the FILESERV-OKFILES listing will
be checked for the file. To delete the file afterwords,
start the line with a # or ^ symbol.
Example .REQ file:
1: joe.schmuck@somewhere.org
2: ; This file has been created by the sysop
3: ; any questions, email joe@mysite.bbs.org ..
4: GIGO
5: e:\files\gateways\gigo0829.zip
6: #f:\bbs\outbound\00010414.mo1
7: ;
8: ; That's all folks!
Line 1: email address
Line 2,3,7,8: Sent to user in a message from fileserv
Line 4: Looks for a file or magic name called GIGO in your fileserv-okfiles
listing. If found, sends it.
Line 5: Absolute path name. Sends the designated file.
Line 6: Absolute path name; mail bundle from fidonet. Deletes when done.